Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1714

reference
661-tree-1
name
1714
tree-preservation-order

undefined

661-tpo-1
uprn
address-text
point
POINT (-1.007872 50.863691)
geometry
MULTIPOLYGON (((-1.007801 50.863684,-1.007804 50.863698,-1.007814 50.863710,-1.007830 50.863720,-1.007849 50.863727,-1.007871 50.863729,-1.007893 50.863727,-1.007913 50.863721,-1.007929 50.863711,-1.007940 50.863699,-1.007943 50.863685,-1.007940 50.863671,-1.007930 50.863658,-1.007915 50.863648,-1.007895 50.863642,-1.007873 50.863639,-1.007851 50.863641,-1.007831 50.863648,-1.007815 50.863657,-1.007805 50.863670,-1.007801 50.863684)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL